- Remove closure safe gaurd because it is unreliable
- change bit mixing scheme to not interleave so un-affected lines has more consistent output hashes
- Standardize on "content ID" nomenclature instead of "content hash"

Co-authored-by: cecli (openai/gemini_cli_local/gemini-2.5-pro)

Co-authored-by: cecli (openai/gemini_cli_local/gemini-2.5-pro)

…s run on event loop of workers and not the main one

…o-retries

feat: add retry logic for empty LLM responses (CLI-49)

… search is a boundary of a block

…icitly

py-cymbal's Cymbal CLI interprets hyphens in search queries as SQL FTS5
NOT operators, causing 'no such column' crashes when the model passes
hyphenated terms like 'vault-store' or 'home-entry'.

Sanitize all symbol queries by replacing hyphens with underscores before
passing to Cymbal. This is semantically correct (code symbols use
underscores, not hyphens) and prevents the crash regardless of which
py-cymbal version is installed.

The root cause is in py-cymbal's Go binary (unquoted FTS5 input) — a
fix has been reported to the Cymbal team (dwash). This cecli-side
workaround provides immediate defense.

…safety

fix(tools): sanitize ExploreCode queries for Cymbal FTS5 safety